Hardware acceleration of boot-up utilizing a non-volatile disk cache

ABSTRACT

A computer system includes a nonvolatile memory positioned between a disk controller and a disk drive storing a boot program, in a computer system. Upon an initial boot sequence, the boot program is loaded into a cache in the nonvolatile memory. Subsequent boot sequences retrieve the boot program from the cache. Cache validity is maintained by monitoring cache misses, and/or by monitoring writes to the disk such that a write to a sector held in the cache results in the cache line for that sector being invalidated until such time as the cache is updated. A filter driver is provided to monitor writes to the disk and determine if a cache line is invalidated.

This application is a continuation of U.S. application Ser. No. 09/417,000 filed on Oct. 13, 1999, now U.S. Pat. No. 6,539.456.

TECHNICAL FIELD OF THE INVENTION

The present invention pertains generally to computers, and more particularly to method and apparatus for speeding the boot-up process in computers.

BACKGROUND OF THE INVENTION

Booting up a computer, and in particular an IBM-compatible personal computer (PC), often takes longer than desired. For example, it is not atypical for a PC using the Windows® 98 operating system to require one minute or more to boot up. This delay can be untenable when the PC needs to be activated on an expedited basis. For instance, if the user needs a phone number quickly, it can be more expeditious to look the number up in a telephone directory as opposed to a PC if the PC requires booting. Thus, unless PC's can be booted more quickly than as is currently the case, their use in applications that require fast initialization is limited. Thus, there is a need for a PC with a shorter boot up time than is currently available.

SUMMARY OF THE INVENTION

The present invention provides method and apparatus for speeding the boot-up of a computer. According to one embodiment of the invention, a boot program stored on a boot disk is cached in a nonvolatile memory, and retrieved by the system from the cache during the boot sequence instead of from the boot disk, thereby increasing the speed of access to the boot program. This and various other embodiments of the invention are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a first embodiment of the apparatus of the invention.

FIGS. 2-5 illustrate various alternate embodiments of the method of using the cache according to the present invention.

FIG. 6 illustrates an alternate embodiment of the apparatus of the invention.

FIG. 7 illustrates yet another embodiment of the method of the invention.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description of the invention reference is made to the accompanying drawings which form a part hereof, and in which is shown, by way of illustration, specific embodiments in which the invention may be practiced. In the drawings, like numerals describe substantially similar components throughout the several views. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. Other embodiments may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present invention.

Referring now to FIG. 1, there is shown a first embodiment of the invention. A computer system 10 includes a Central Processing Unit (CPU) 12, a boot disk 14 storing a boot program 16 used by the computer system 10 to boot, and a nonvolatile random access memory 18 used as a disk cache. Memory 18 receives all or a portion of the boot program 16 from the boot disk 14 and stores it for access by the CPU 12 so that the computer system 10 can boot in whole or in part from the disk cache in memory 18. A data bus 20 couples the CPU 12 to a controller 22 that controls the boot disk 14, and a cache controller 24 is coupled between the bus 20 and the boot disk 14, and wherein the memory 18 is coupled to the cache controller 22. In one example embodiment, the computer system 10 may comprise an IBM-compatible computer with a Pentium class microprocessor and an IDE controller for controller 22, or an Apple Macintosh computer with a Motorola microprocessor. The invention, however, is not limited in this respect, and other types of computer systems and processors can be used. Nonvolatile memory 18 may be a FLASH memory, or any suitable form of nonvolatile memory, and, preferably in at least some embodiments of the invention, random access memory.

In operation, the computer system 10 operates under the control of an operating system 26, which includes as a portion thereof boot program 16. Boot program 16 has a boot-time disk footprint of a ascertainable size. The memory 18 is sized to be substantially as large as the boot-time disk footprint, so that the boot program 16 can be cached in the memory 18. However, the memory 18 could be smaller than the footprint, and store only a portion of the entire boot program 16. Alternatively, memory 18 could exceed the size of program 16. All or a portion of boot program 16 can therefore be stored in memory 18, from where it can be more quickly retrieved, as opposed to being retrieved from the boot disk 14, during boot-up of the system 10. If only a portion of the boot program 16 is stored in memory 18, that portion may be retrieved therefrom, with the remaining portion retrieved from the boot disk 14.

According to another example embodiment, the boot program cache in memory 18 is formed of lines, the boot program 16 is stored in linear sectors on the boot disk 14, and the lines of the cache are mapped to the linear sectors of the boot disk 14 read in a boot sequence upon boot up of system 10. Referring to FIGS. 2-5, there is shown an example method for using the boot program cache. Initially, the cache lines are marked invalid (30). The cache is loaded with data from sectors of disk 14 read during an initial boot sequence (32). As shown in FIG. 3, during boots of the system 10 subsequent to the initial boot sequence, data in the cache is used (34) instead of the corresponding sector data from the boot disk, if the sector data in the cache is valid (33). Otherwise, the boot program or the disk is used (35). According to another example variant of this embodiment shown in FIG. 4, if data is written to a sector read during the initial boot sequence (36), the cache lines corresponding to the sector are marked invalid (37). The invalid cache line can be subsequently replaced with new data from the boot disk and the cache line marked valid (38). According to yet another example embodiment of the method of the present invention, illustrated in FIG. 5, cache coherency is maintained by detecting cache misses (40), and if a miss is detected, aging the cache, to invalidate lines from the cache (41). According to one approach, the cache is aged in a first-in first-out (FIFO) manner.

According to yet another embodiment of the invention diagrammatically illustrated in FIG. 6, a filter driver 50 is positioned between the operating system 26 and the disk controller 22, and the filter driver 50 has access to all input-output (I/O) requests to the boot disk 14, and to a cache map 52 in cache controller 24. Filter driver 50 can detect writes to the disk 14 which are in the same sector as a sector in the cache. In one embodiment, filter driver 50 can monitor all I/O operations without significantly slowing performance of the system.

According to a method of operation using the embodiment of FIG. 6, illustrated in FIG. 7, if a disk sector cached in the cache is changed (60), as detected by filter driver 50, the corresponding cache line is invalidated (61). The invalidated line can be refreshed with the correct contents during the next boot sequence (62). In one embodiment, the cache is not updated by the filter driver so that performance is not degraded. However, according to another embodiment, the cache is refreshed during the write operation to the corresponding sector in the disk drive (64) using a cache write-back queue.

Thus, as described above, there is provided method and apparatus for speeding the boot-up of a computer. The invention is applicable to all manner of computer systems, including appliance-like, sealed case systems, where the loadable files and configuration are seldom changed. 

What is claimed is:
 1. A method comprising: storing a boot program used by an information-processing system in a nonvolatile memory cache which receives all or a portion of the boot program from a system boot disk; accessing the boot program or portion thereof stored in the cache by a CPU so that the information-processing system can boot in whole or in part from the cache: wherein during the initial system boot, the cache is loaded with data from the system boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, wherein if boot data is subsequently written to the boot data on the system boot disk, the corresponding data in the cache is marked invalid, wherein during a system boot subsequent to the initial boot when cache data is marked invalid, the invalid data is replaced with data from the boot disk and the replacement data is marked valid.
 2. The method of claim 1, further including: holding operating system components in the cache, the components necessary for system boot.
 3. The method of claim 1, further including: controlling the system boot disk with an IDE controller; organizing the cache data according to sectors on the system boot disk; mapping the organized cache data to sectors in the system boot disk holding the boot program or portion thereof, wherein the organized and mapped cache data includes the boot program or portion thereof.
 4. The method of claim 1, further comprising: providing a data bus that couples the CPU to a cache controller coupled between the bus and the boot disk, wherein the nonvolatile memory cache is coupled to the cache controller.
 5. A method comprising: storing a boot program used by an information-processing system in a nonvolatile memory cache which receives all or a portion of the boot program from a system boot disk; accessing the boot program or portion thereof stored in the cache by a CPU so that the information-processing system can boot in whole or in part from the cache: wherein the cache data is initially marked invalid, wherein during the initial system boot, the cache is loaded with data from the system boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, and wherein cache coherency is maintained by detecting cache misses, and if a miss is detected, the cache is aged, to invalidate all or a portion of the cache data.
 6. The method of claim 5, further including: controlling the system boot disk with an IDE controller; organizing the cache data according to sectors on the system boot disk; mapping the organized cache data to sectors in the system boot disk holding the boot program or portion thereof.
 7. The method of claim 5, further including: holding operating system components in the cache, the components necessary for system boot.
 8. The method of claim 5, wherein the cache is aged in a first-in first-out (FIFO) manner.
 9. A method comprising: storing a boot program used by an information-processing system in a nonvolatile memory cache which receives all or a portion of the boot program from a system boot disk; accessing the boot program or portion thereof stored in the cache by a CPU so that the information-processing system can boot in whole or in part from the cache: wherein the cache data is initially marked invalid, wherein during the initial system boot, the cache is loaded with data from the system boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, wherein a filter driver is positioned between the CPU and the system boot disk, wherein the filter driver has access to all input-output (I/O) requests to the boot disk, wherein the filter driver has access to a cache map and detect writes to the system boot disk data that is also stored in the cache.
 10. The method of claim 9, further including: controlling the system boot disk with an IDE controller; organizing the cache data according to sectors on the system boot disk; mapping the organized cache data to sectors in the system boot disk holding the boot program or portion thereof.
 11. The method of claim 10, wherein the cache is not updated by the filter driver.
 12. The method of claim 10, further including: replacing boot data marked invalid in the organized cache during a system boot with data from the sectors in the system boot disk holding the boot program or portion thereof; marking the replacement cache data as valid.
 13. The method of claim 10, further including: refreshing cache data during a write operation to the corresponding mapped boot disk sector.
 14. A method comprising storing a boot program used by an information-processing system in a nonvolatile memory cache which receives all or a portion of the boot program from a system boot disk, the boot program or portion thereof stored in the cache for access by a CPU so that the system can boot in whole or in part from the cache, further wherein the cache is first loaded on an initial system boot and the loaded program or portion thereof is marked valid, further wherein the boot program or portion thereof loaded in the cache is used to perform system boots if the boot program or portion thereof continues to be marked valid, further wherein the boot program or portion thereof stored in the cache is marked invalid when the boot program is modified on the system boot disk.
 15. The method according to claim 14, wherein the system boot disk is a local system boot disk.
 16. The method of claim 14, further wherein the boot program or portion thereof is refreshed in the cache and marked valid during the next system boot after the modifying of the boot program or portion thereof on the system boot disk.
 17. The method of claim 14, further wherein the cache is refreshed following a system boot disk write during a system shutdown process.
 18. The method of claim 14, further wherein the cache is refreshed following a system boot disk modification upon the occurrence of an operating system idle event, the operating system executing on the information-processing system.
 19. An information-processing system comprising: a CPU; a boot disk storing a boot program used by the system to boot; and a nonvolatile memory cache receiving all or a portion of the boot program from the boot disk and storing it for access by the CPU so that the computer system can boot in whole or in part from the cache: wherein data in the cache is initially marked invalid, wherein during the initial system boot, the cache is loaded with data from the boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, wherein if boot data is subsequently written to the boot data on the boot disk, the corresponding data in the cache is marked invalid.
 20. The information-processing system of claim 19, wherein during a system boot subsequent to the initial boot when cache data is marked invalid, the invalid data is replaced with data from the boot disk and the replacement data is marked valid.
 21. The information-processing system of claim 19, further including: a disk controller for controlling the boot disk.
 22. The information-processing system claim 21, wherein the disk controller is an IDE controller.
 23. The information-processing system of claim 19, further wherein the cache data is organized according to sectors on the boot disk and the organized cache data is mapped to sectors in the system boot disk holding the boot program.
 24. An information-processing system comprising: a CPU; a boot disk storing a boot program used by the system to boot; and a nonvolatile memory cache receiving all or a portion of the boot program from the boot disk and storing it for access by the CPU so that the system can boot in whole or in part from the cache: wherein data in the cache is initially marked invalid, wherein during the initial system boot, the cache is loaded with data from the system boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, and wherein cache coherency is maintainable by detecting cache misses, and if a miss is detected, the cache is aged, to invalidate all or a portion of the cache data.
 25. The information-processing system of claim 24, wherein the cache is aged in a first-in first-out (FIFO) manner.
 26. An information-processing system comprising: a CPU; a boot disk storing a boot program used by the system to boot; and a nonvolatile memory cache receiving all or a portion of the boot program from the boot disk and storing it for access by the CPU so that the system can boot in whole or in part from the cache: wherein data in the cache is initially marked invalid, wherein during the initial system boot, the cache is loaded with data from the system boot disk and the loaded data is marked valid, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, wherein a filter driver is positioned between the CPU and the system boot disk, wherein the filter driver has access to all input-output (I/O) requests to the boot disk, wherein the filter driver has access to a cache map and detect writes to the system boot disk data that is also stored in the cache.
 27. The information-processing system of claim 26, wherein the cache is not updated by the filter driver.
 28. The information-processing system of claim 26, further including: a disk controller for controlling the boot disk.
 29. The information-processing system of claim 28, further wherein: the cache data is organized according to sectors on the boot disk; the organized cache data is mapped to sectors in the system boot disk holding the boot program or portion thereof.
 30. The information-processing system of claim 29, further wherein if a boot disk sector is changed, the corresponding mapped cache data is invalidated, and refreshed with the correct contents during the next boot sequence.
 31. The information-processing system of claim 29, wherein the cache is refreshed during the write operation to the corresponding sector in the boot disk.
 32. A computer system, comprising: a CPU; a boot disk storing a boot program used by the computer system to boot; a nonvolatile memory disk cache receiving all or a portion of the boot program from the boot disk and storing it for access by the CPU, so that the computer system can boot in whole or in part from the disk cache; and a controller for controlling the boot disk, wherein the cache is loaded with data from sectors read during an initial boot sequence, wherein the loaded cache data is mapped to the data from which it is loaded, wherein during boots of the system subsequent to the initial boot, sequence sector data in the cache is used instead of the corresponding sector data from the boot disk if the sector data in the cache is valid, and wherein if data is written to a sector read during the initial boot sequence, the cache data corresponding to the sector is marked invalid.
 33. The computer system of claim 32, further comprising: a data bus coupled to the CPU; and a cache controller coupled between the bus and the boot disk, wherein the nonvolatile memory disk cache is coupled to the cache controller.
 34. The computer system of claim 32, wherein the computer system operates under the control of an operating system, and wherein the operating system has a boot-time disk footprint size and the cache is sized substantially as large as the size of the footprint.
 35. The computer system of claim 32, wherein the invalid cache data is replaced with valid data from the boot disk and the cache replacement data is marked valid.
 36. The computer system of claim 32, further comprising: a data bus coupled to the CPU; and a cache controller coupled between the bus and the boot disk, wherein the cache is coupled to the cache controller.
 37. A computer system, comprising: a CPU; a boot disk storing a boot program used by the computer system to boot; a nonvolatile memory cache receiving all or a portion of the boot program from the boot disk and storing it for access by the CPU, so that the computer system can boot in whole or in part from the disk cache; a controller for controlling the boot disk; and a filter driver between the CPU and the controller, wherein data in the cache is initially marked invalid, wherein the cache is loaded with data from sectors read during an initial boot sequence, wherein the loaded cache data is mapped to the data from which it is loaded, wherein during boots of the system subsequent to the initial boot, data in the cache is used instead of the corresponding data from the boot disk if the data in the cache is valid, wherein the filter driver has access to all input-output (110) requests to the boot disk, and wherein the filter driver has access to a cache map and can detect writes to the disk which correspond to data in the cache.
 38. The computer system of claim 37, further wherein if the boot program or portion thereof is changed, the corresponding cache data is invalidated, and refreshed with the correct contents during the next boot sequence.
 39. The computer system of claim 37, wherein the cache is not updated by the filter driver.
 40. The computer system of claim 39, wherein the cache is refreshed during the write operation to the corresponding data in the boot disk. 